tk88 vna .com

Product description



　　Hi Robert,

　　Memory allocation in SAP is rather complex, so I’ll just do a basic run down

　　here. For an individual (DIA)log work process, memory is allocated as

　　follows:

　　(1) An initial portion of the Roll area (determined by parameter

　　ztta/roll_first)

　　(2) Extended memory is used until:

　　(a) the total amount of extended memory allocated to SAP on the

　　application server is exhausted

　　–OR–

　　(b) the user exhausts the single user quota of shared memory (determined

　　by parameter ztta/roll_extension)

　　(3) The remaining roll area memory for the DIA process is used

　　If steps (1) - (3) still do not yield enough memory for the DIA process, you

　　go to:

　　(4) System allocates Heap Memory to the DIA process

　　This is when you get the PRIV mode indication in SM66. There are various

　　problems with PRIV mode, which is why the system highlights it for you. For

　　one thing, while a user is in a transaction that forced the DIA WP into

　　PRIV, no other user can access that WP. This totally contravenes the

　　multi-threaded work process structure of SAP until the user completes the

　　transaction AND exits out of it (i.e. if it is a report and they leave it

　　displayed on the screen rather than backing out, the WP will remained locked

　　off in PRIV, making it useless to every other user in the system).

　　Anyway, that’s a quick explanation. Feel free to reply on list if you need

　　further details. Hope this helps somewhat.

　　Katherine